Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1949

reference
29-tree-1
name
1949
tree-preservation-order

undefined

29-tpo-1
uprn
address-text
point
POINT (-0.974493 50.849282)
geometry
MULTIPOLYGON (((-0.974436 50.849276,-0.974439 50.849287,-0.974447 50.849297,-0.974459 50.849306,-0.974475 50.849311,-0.974492 50.849313,-0.974510 50.849311,-0.974526 50.849306,-0.974538 50.849298,-0.974547 50.849288,-0.974550 50.849277,-0.974547 50.849266,-0.974539 50.849256,-0.974527 50.849248,-0.974511 50.849243,-0.974494 50.849241,-0.974476 50.849242,-0.974460 50.849247,-0.974448 50.849255,-0.974439 50.849265,-0.974436 50.849276)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL